Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-69405 | APSC-DV-000830 | SV-84027r1_rule | Medium |
Description |
---|
Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). Knowing when a user successfully or unsuccessfully logged on to the application is critical information that aids in forensic analysis. |
STIG | Date |
---|---|
Application Security and Development Security Technical Implementation Guide | 2020-06-12 |
Check Text ( C-69821r1_chk ) |
---|
Review and monitor the application logs. Authenticate to the application and observe if the log includes an entry to indicate the user’s authentication was successful. Terminate the user session by logging out. Reauthenticate using invalid user credentials and observe if the log includes an entry to indicate the authentication was unsuccessful. If successful and unsuccessful logon events are not recorded in the logs, this is a finding. |
Fix Text (F-75579r1_fix) |
---|
Configure the application or application server to write a log entry when successful and unsuccessful logon events occur. |